Troubleshooting with common errors - Backend
Overview
Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and explain how to resolve the problem. The first step in the troubleshooting process is to describe the problem completely.
Steps of Troubleshooting
- Gather information and Define the problem
- Analyze the data and Determine the most probable cause
- Create a plan of action
- Implement the solution
- Analyze the results
- Document the process
Common Errors
OGS Login: If Users are not able to login to Navida PRO application, we shall check the OGS authentication is success. In case any failure in authbroker response we should report that to respective team to rectify the same
JWS Token Expiry: There might be scenarion that log files might be printed with Error message due to JWS Token Expiry. We shall inform users to retry the login
Master Profile: Some times Profile data is not shown in Master profile page in Navida Pro App. This could be the reason where we are not getting proper response from OGS Profile Retreival call.
Database Permission Issues: Every Read and Write call into database is authorized. If access provided explicitly then the operations will happen. Otherwise appropriate authorization error message will appear in logs which will help to inform the team to take action.
Data not Persisting - Kafka: Database persist operation is handled through Kafka which is also authorized. If there is no proper permission is granted to Kafka topics, database operation might fail.